Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3f8d2a10de8a4e4c666b3fab3f445170376a2ea35e18e3c816986e2e2a5a4bb7

Tx prefix hash: 609a5d5e4e08e52499195a189521b4c4cd1d5c2403271225c80cab4bbf94e839
Tx public key: 136bb10c07445e553678b84de5c8ff1c3431e55047a06ffe7e9ff9d741b051eb
Timestamp: 1726939872 Timestamp [UCT]: 2024-09-21 17:31:12 Age [y:d:h:m:s]: 00:153:19:57:16
Block: 1115095 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109717 RingCT/type: yes/0
Extra: 01136bb10c07445e553678b84de5c8ff1c3431e55047a06ffe7e9ff9d741b051eb02110000001091e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 554ae80fb8730eb055c1a4600f45ec836fd7b7b8c869eac8e8d8047e4a8c0aa7 0.600000000000 1595106 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": 1115105, "vin": [ { "gen": { "height": 1115095 } } ], "vout": [ { "amount": 600000000, "target": { "key": "554ae80fb8730eb055c1a4600f45ec836fd7b7b8c869eac8e8d8047e4a8c0aa7" } } ], "extra": [ 1, 19, 107, 177, 12, 7, 68, 94, 85, 54, 120, 184, 77, 229, 200, 255, 28, 52, 49, 229, 80, 71, 160, 111, 254, 126, 159, 249, 215, 65, 176, 81, 235, 2, 17, 0, 0, 0, 16, 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