Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7887adf5327bf43930d7e48370d70fdcfafa1c1d3911ca5255a746a1e0a0b056

Tx prefix hash: 70806e4d4bf040b6321bdc52c1ecd72f790022e097d639be6863dffd8be8d5ff
Tx public key: 32cbcb878ddfb09ab546d1c129d13c9cd0a17f03ef1d84b69444482c064da864
Timestamp: 1738361545 Timestamp [UCT]: 2025-01-31 22:12:25 Age [y:d:h:m:s]: 00:341:21:29:20
Block: 1209359 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 242191 RingCT/type: yes/0
Extra: 0132cbcb878ddfb09ab546d1c129d13c9cd0a17f03ef1d84b69444482c064da864021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0a3bfd4bd7be0aa08d844cdf518f62ca3456df5449c17a20a02ed4f2df8c3147 0.600000000000 1696100 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": 1209369, "vin": [ { "gen": { "height": 1209359 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0a3bfd4bd7be0aa08d844cdf518f62ca3456df5449c17a20a02ed4f2df8c3147" } } ], "extra": [ 1, 50, 203, 203, 135, 141, 223, 176, 154, 181, 70, 209, 193, 41, 209, 60, 156, 208, 161, 127, 3, 239, 29, 132, 182, 148, 68, 72, 44, 6, 77, 168, 100, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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