Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1be72ed5fc7608633f289b195627fb71b034c85f466c8bbbbde5adf806daeea4

Tx prefix hash: dca875b708056742fc969710fc352f9e45343665209b7903099ef3c16759e4dd
Tx public key: 317249ddcb02bcf63b5e97ca8ee596b0f6b144a80a52f60151cb2afd19d930ae
Timestamp: 1719163868 Timestamp [UCT]: 2024-06-23 17:31:08 Age [y:d:h:m:s]: 01:137:16:31:55
Block: 1050606 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 356974 RingCT/type: yes/0
Extra: 01317249ddcb02bcf63b5e97ca8ee596b0f6b144a80a52f60151cb2afd19d930ae0211000000020fbbc4c5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aa7d20a3babae430f4162d82bb308d1cb0ee0a1b7feea4f849647853aef02287 0.600000000000 1520781 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": 1050616, "vin": [ { "gen": { "height": 1050606 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aa7d20a3babae430f4162d82bb308d1cb0ee0a1b7feea4f849647853aef02287" } } ], "extra": [ 1, 49, 114, 73, 221, 203, 2, 188, 246, 59, 94, 151, 202, 142, 229, 150, 176, 246, 177, 68, 168, 10, 82, 246, 1, 81, 203, 42, 253, 25, 217, 48, 174, 2, 17, 0, 0, 0, 2, 15, 187, 196, 197, 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