Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c04d570191da089af588b559e8909abd8ed58e03e19d3e37c4f0579e79e6a511

Tx prefix hash: 70152d92025c70e5307e73075080fde1ac41f8963b091538bc48d91c430c8342
Tx public key: 88773554051ff8f997fe3d2b51f10e7172e8ab719aa28f35ee7a5ad33bea3fdf
Timestamp: 1714184136 Timestamp [UCT]: 2024-04-27 02:15:36 Age [y:d:h:m:s]: 00:324:02:39:05
Block: 1009329 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 231711 RingCT/type: yes/0
Extra: 0188773554051ff8f997fe3d2b51f10e7172e8ab719aa28f35ee7a5ad33bea3fdf02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ff4d767eb7b50b620c5964e5837ad4f9a74c5c35ad2af7df171d21932857b37b 0.600000000000 1470971 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": 1009339, "vin": [ { "gen": { "height": 1009329 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ff4d767eb7b50b620c5964e5837ad4f9a74c5c35ad2af7df171d21932857b37b" } } ], "extra": [ 1, 136, 119, 53, 84, 5, 31, 248, 249, 151, 254, 61, 43, 81, 241, 14, 113, 114, 232, 171, 113, 154, 162, 143, 53, 238, 122, 90, 211, 59, 234, 63, 223, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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