Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 70ff29901133d81aac7a7a10aeadfe6d4a97fc731c77053c25b65e95ac331ed5

Tx prefix hash: 5641ed18f773395349231e01e33047cc58ddc41107a930c7caee2fa5428fddee
Tx public key: ce230bc728e1f6e5e0f2051c86dadccc82c711022d0b9e60cb9aca260b1f3be6
Timestamp: 1704147704 Timestamp [UCT]: 2024-01-01 22:21:44 Age [y:d:h:m:s]: 01:084:07:48:15
Block: 926128 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 321356 RingCT/type: yes/0
Extra: 01ce230bc728e1f6e5e0f2051c86dadccc82c711022d0b9e60cb9aca260b1f3be60211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 89df14003df98ddc503ff2f167ac734254445d514153bcbcd58c3a91e2e0a3b3 0.600000000000 1383902 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": 926138, "vin": [ { "gen": { "height": 926128 } } ], "vout": [ { "amount": 600000000, "target": { "key": "89df14003df98ddc503ff2f167ac734254445d514153bcbcd58c3a91e2e0a3b3" } } ], "extra": [ 1, 206, 35, 11, 199, 40, 225, 246, 229, 224, 242, 5, 28, 134, 218, 220, 204, 130, 199, 17, 2, 45, 11, 158, 96, 203, 154, 202, 38, 11, 31, 59, 230, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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