Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d229fd6907200d0902f1a53947003f23a8d1b086658800c328ae0d8f928550bd

Tx prefix hash: 0c410c554ffb155d4ac007aad48b359b0d89f646fdb37dced58d4bd21d0c6714
Tx public key: 3c316b1ae34b22a6c2bda09d69bb04df2eeca52245e7a0af3201c6e31c0b0a9a
Timestamp: 1712593982 Timestamp [UCT]: 2024-04-08 16:33:02 Age [y:d:h:m:s]: 01:205:12:29:48
Block: 996125 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 405586 RingCT/type: yes/0
Extra: 013c316b1ae34b22a6c2bda09d69bb04df2eeca52245e7a0af3201c6e31c0b0a9a02110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cb7711a4e347a9d3dc47257ad74384a3fce598b5c2a0249cddb6414d460dc2a9 0.600000000000 1456541 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": 996135, "vin": [ { "gen": { "height": 996125 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cb7711a4e347a9d3dc47257ad74384a3fce598b5c2a0249cddb6414d460dc2a9" } } ], "extra": [ 1, 60, 49, 107, 26, 227, 75, 34, 166, 194, 189, 160, 157, 105, 187, 4, 223, 46, 236, 165, 34, 69, 231, 160, 175, 50, 1, 198, 227, 28, 11, 10, 154, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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