Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2dbc142d9196088b0d29c31e0a752d5503f621b29e867a815d2937f132f290e5

Tx prefix hash: 673ac3cd38373295c871f81639ece6ac2cd459332f6c8cf4b6f64e6bcaed0714
Tx public key: 0472632992c6616f14d95e03c9b6d51cd6fe6c1b7acaecaa46a455ff6ad2fa8b
Timestamp: 1706070492 Timestamp [UCT]: 2024-01-24 04:28:12 Age [y:d:h:m:s]: 00:296:06:27:51
Block: 942043 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 212157 RingCT/type: yes/0
Extra: 010472632992c6616f14d95e03c9b6d51cd6fe6c1b7acaecaa46a455ff6ad2fa8b02110000000479bda3be000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d08c9346df11a680e7e4e3998cde2255976c49ac298bddc5988fa4c7a74e8626 0.600000000000 1400209 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": 942053, "vin": [ { "gen": { "height": 942043 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d08c9346df11a680e7e4e3998cde2255976c49ac298bddc5988fa4c7a74e8626" } } ], "extra": [ 1, 4, 114, 99, 41, 146, 198, 97, 111, 20, 217, 94, 3, 201, 182, 213, 28, 214, 254, 108, 27, 122, 202, 236, 170, 70, 164, 85, 255, 106, 210, 250, 139, 2, 17, 0, 0, 0, 4, 121, 189, 163, 190, 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