Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 000c6185bc83a29b8902da4fa5e37bb445c4e3b4f9d88afa2e64badceb860b29

Tx prefix hash: bfa74c880701af686335a028d4d0e4b4ac09ccf76ecbf7a0aa02aec368283f23
Tx public key: dd94705624afb0069af54d8d63e2050f16b89c994d0bb345e9119a435f0ab0b7
Timestamp: 1703784585 Timestamp [UCT]: 2023-12-28 17:29:45 Age [y:d:h:m:s]: 01:063:20:48:02
Block: 923122 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 306732 RingCT/type: yes/0
Extra: 01dd94705624afb0069af54d8d63e2050f16b89c994d0bb345e9119a435f0ab0b702110000000a0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d3ab5aef3adeb04de3c7c64e59a2bbc0c747cd549d321d6e515b1fc2b08c7b73 0.600000000000 1380840 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": 923132, "vin": [ { "gen": { "height": 923122 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d3ab5aef3adeb04de3c7c64e59a2bbc0c747cd549d321d6e515b1fc2b08c7b73" } } ], "extra": [ 1, 221, 148, 112, 86, 36, 175, 176, 6, 154, 245, 77, 141, 99, 226, 5, 15, 22, 184, 156, 153, 77, 11, 179, 69, 233, 17, 154, 67, 95, 10, 176, 183, 2, 17, 0, 0, 0, 10, 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