Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d0c0e6b193120f7300884f0fc8d2cfbc2aa37e47842e5ccbcffc688c1c3d83e6

Tx prefix hash: 80a9c12f6c5f6c4008183883dfb2cc461055a6105f3d89bc3bab3c6e3fc5a350
Tx public key: 5245bb42f6bcd9825eda61baa751ddbd209f4c05444fcec5a9c970c19310d1ad
Timestamp: 1728429373 Timestamp [UCT]: 2024-10-08 23:16:13 Age [y:d:h:m:s]: 01:044:00:57:51
Block: 1127437 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 289863 RingCT/type: yes/0
Extra: 015245bb42f6bcd9825eda61baa751ddbd209f4c05444fcec5a9c970c19310d1ad02110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dc03de34fe04b5f956ddc15162be7b58041b8b47ccd6c6594c9a5632aed80801 0.600000000000 1610242 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": 1127447, "vin": [ { "gen": { "height": 1127437 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dc03de34fe04b5f956ddc15162be7b58041b8b47ccd6c6594c9a5632aed80801" } } ], "extra": [ 1, 82, 69, 187, 66, 246, 188, 217, 130, 94, 218, 97, 186, 167, 81, 221, 189, 32, 159, 76, 5, 68, 79, 206, 197, 169, 201, 112, 193, 147, 16, 209, 173, 2, 17, 0, 0, 0, 2, 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