Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cad1524f62adfdb6b26549889573035e11e955549b71d1b28efd38fcb9ba9cbd

Tx prefix hash: dbcb9c73c1e3100496adcdb0c425d7a5bd04b96e0e029d34780934b2a3a9c95a
Tx public key: 94038e434a95c567f07efcebf26e44fefc5aebaae9bf525e2f1723f6a519dceb
Timestamp: 1577744174 Timestamp [UCT]: 2019-12-30 22:16:14 Age [y:d:h:m:s]: 05:035:05:32:19
Block: 35352 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1174881 RingCT/type: yes/0
Extra: 0194038e434a95c567f07efcebf26e44fefc5aebaae9bf525e2f1723f6a519dceb021100000004d81c26c0000000000000000000

1 output(s) for total of 468.667678006000 dcy

stealth address amount amount idx
00: b41c7e8b0529dfa4c97e8c50e28aa2f9a69886b002d636745dd8ff87da7c8c68 468.667678006000 59565 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": 35362, "vin": [ { "gen": { "height": 35352 } } ], "vout": [ { "amount": 468667678006, "target": { "key": "b41c7e8b0529dfa4c97e8c50e28aa2f9a69886b002d636745dd8ff87da7c8c68" } } ], "extra": [ 1, 148, 3, 142, 67, 74, 149, 197, 103, 240, 126, 252, 235, 242, 110, 68, 254, 252, 90, 235, 170, 233, 191, 82, 94, 47, 23, 35, 246, 165, 25, 220, 235, 2, 17, 0, 0, 0, 4, 216, 28, 38, 192, 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