Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 04145a82072f0d7a5d2394f255eab4f1ecca3e9eca66f46069de887c0ab2ae76

Tx prefix hash: aa6344b4cc4751b1f7125d9c65169a8be0970a5f127970dea4f4af13771d621d
Tx public key: c081e61e815af368770d17325adb14e693069fad7b4e4e5ef4f4768fa4c3ec00
Timestamp: 1726007582 Timestamp [UCT]: 2024-09-10 22:33:02 Age [y:d:h:m:s]: 00:245:19:17:32
Block: 1107368 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175541 RingCT/type: yes/0
Extra: 01c081e61e815af368770d17325adb14e693069fad7b4e4e5ef4f4768fa4c3ec0002110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 775730fbdf958e74b78be5d13ece4476c2aa2ee9b5b3300ca68c7ac25a842866 0.600000000000 1584979 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1107378, "vin": [ { "gen": { "height": 1107368 } } ], "vout": [ { "amount": 600000000, "target": { "key": "775730fbdf958e74b78be5d13ece4476c2aa2ee9b5b3300ca68c7ac25a842866" } } ], "extra": [ 1, 192, 129, 230, 30, 129, 90, 243, 104, 119, 13, 23, 50, 90, 219, 20, 230, 147, 6, 159, 173, 123, 78, 78, 94, 244, 244, 118, 143, 164, 195, 236, 0, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8