Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 06137f457c977e749928c12d18beda1a373b8ebdd9565a53e562f765d91ae02f

Tx prefix hash: 544a0444ac737b82f651b39d2568152e92c65472be7ec8e5b302488c76430c3a
Tx public key: b9ac816b0b4349ba821b9ba2e536fcdc13929afe516b26108e9f522fde5c82f7
Timestamp: 1717070185 Timestamp [UCT]: 2024-05-30 11:56:25 Age [y:d:h:m:s]: 00:291:00:13:52
Block: 1033267 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 207997 RingCT/type: yes/0
Extra: 01b9ac816b0b4349ba821b9ba2e536fcdc13929afe516b26108e9f522fde5c82f70211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d3f9b2e5e0a941ecb1188c79cddfc9dac0c49b4aaf99230898b0e74bd0fc1114 0.600000000000 1501730 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": 1033277, "vin": [ { "gen": { "height": 1033267 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d3f9b2e5e0a941ecb1188c79cddfc9dac0c49b4aaf99230898b0e74bd0fc1114" } } ], "extra": [ 1, 185, 172, 129, 107, 11, 67, 73, 186, 130, 27, 155, 162, 229, 54, 252, 220, 19, 146, 154, 254, 81, 107, 38, 16, 142, 159, 82, 47, 222, 92, 130, 247, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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