Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b599e6c690c35123be0794961c70fa161d83f30f5e1ed45e6fdf951833df4c5e

Tx prefix hash: 452ef5819b935950bd94fd6e752d5b2af606cb0cbf4026cc0eff0dccea47a7fa
Tx public key: 432d9f0f4462c5f1a0de85c535ae6a6e3e839bfd40e720fb979a02eaf4762316
Timestamp: 1728091386 Timestamp [UCT]: 2024-10-05 01:23:06 Age [y:d:h:m:s]: 00:160:23:30:33
Block: 1124635 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 114860 RingCT/type: yes/0
Extra: 01432d9f0f4462c5f1a0de85c535ae6a6e3e839bfd40e720fb979a02eaf4762316021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6a0ab829b6493eaa3caeeb3b32775415010c2e62468f047e8bfab517a418c4b0 0.600000000000 1607288 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": 1124645, "vin": [ { "gen": { "height": 1124635 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6a0ab829b6493eaa3caeeb3b32775415010c2e62468f047e8bfab517a418c4b0" } } ], "extra": [ 1, 67, 45, 159, 15, 68, 98, 197, 241, 160, 222, 133, 197, 53, 174, 106, 110, 62, 131, 155, 253, 64, 231, 32, 251, 151, 154, 2, 234, 244, 118, 35, 22, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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