Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 247603796cd8e33c418fad95ba1951f46fddd66d094ea8f4ab63192b2558f1d0

Tx prefix hash: c178329e21aed367f1760565ad1817482f10c13a0c1d1fd1f749903fc8e02620
Tx public key: 146bfd9646e4b4de4d7fb3ecc0b2df4fbd05ebb72b9eb6cac3c38642600cdeb2
Timestamp: 1657047780 Timestamp [UCT]: 2022-07-05 19:03:00 Age [y:d:h:m:s]: 03:118:17:38:03
Block: 537367 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 864569 RingCT/type: yes/0
Extra: 01146bfd9646e4b4de4d7fb3ecc0b2df4fbd05ebb72b9eb6cac3c38642600cdeb2021100000010a8c141c5000000000000000000

1 output(s) for total of 10.173730009000 dcy

stealth address amount amount idx
00: bb19a74ddc1ba2f66216cb4f45c336df8bc97e753270f1bae9df2a8f2c583f0d 10.173730009000 967244 of 0

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": 537377, "vin": [ { "gen": { "height": 537367 } } ], "vout": [ { "amount": 10173730009, "target": { "key": "bb19a74ddc1ba2f66216cb4f45c336df8bc97e753270f1bae9df2a8f2c583f0d" } } ], "extra": [ 1, 20, 107, 253, 150, 70, 228, 180, 222, 77, 127, 179, 236, 192, 178, 223, 79, 189, 5, 235, 183, 43, 158, 182, 202, 195, 195, 134, 66, 96, 12, 222, 178, 2, 17, 0, 0, 0, 16, 168, 193, 65, 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