Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2e3d5f6e0ed836a1ef2e996e2b6844201c998b5e41ac8e5efb8c62203271165d

Tx prefix hash: 029cdf266be0dfdc3e6733e402cc9b0e91c9ab9309cafd183236b5496403ae28
Tx public key: a4bdc86af004c95fe60797d5a8040a304b466823ab7315485a4cd523b4b20881
Timestamp: 1736378941 Timestamp [UCT]: 2025-01-08 23:29:01 Age [y:d:h:m:s]: 00:085:05:47:56
Block: 1193211 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 60694 RingCT/type: yes/0
Extra: 01a4bdc86af004c95fe60797d5a8040a304b466823ab7315485a4cd523b4b20881021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 339b87c34d91a00e2c5d9d74ad6f28f044f351a2c82c763df72d073126004570 0.600000000000 1679770 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": 1193221, "vin": [ { "gen": { "height": 1193211 } } ], "vout": [ { "amount": 600000000, "target": { "key": "339b87c34d91a00e2c5d9d74ad6f28f044f351a2c82c763df72d073126004570" } } ], "extra": [ 1, 164, 189, 200, 106, 240, 4, 201, 95, 230, 7, 151, 213, 168, 4, 10, 48, 75, 70, 104, 35, 171, 115, 21, 72, 90, 76, 213, 35, 180, 178, 8, 129, 2, 17, 0, 0, 0, 7, 0, 127, 151, 138, 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