Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d86ca509da1603898480f031b9fa53d2ebd628b74d4b0c12833aee60058beb37

Tx prefix hash: f096e36249fd3fbdbcbe9fd0c71d50d1f4e751c8c3a4616b04e06c71e5930fe9
Tx public key: 6ca7e13ba2eccac1009d40dede1d10cfcc645c85b7489cf745e60c89e8797dbb
Timestamp: 1729603792 Timestamp [UCT]: 2024-10-22 13:29:52 Age [y:d:h:m:s]: 00:213:00:46:47
Block: 1137139 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 152094 RingCT/type: yes/0
Extra: 016ca7e13ba2eccac1009d40dede1d10cfcc645c85b7489cf745e60c89e8797dbb0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bd372cdfe29676de9a5392a6c201d7b6006b5a40040e99048be3a61b90f534e4 0.600000000000 1620576 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": 1137149, "vin": [ { "gen": { "height": 1137139 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bd372cdfe29676de9a5392a6c201d7b6006b5a40040e99048be3a61b90f534e4" } } ], "extra": [ 1, 108, 167, 225, 59, 162, 236, 202, 193, 0, 157, 64, 222, 222, 29, 16, 207, 204, 100, 92, 133, 183, 72, 156, 247, 69, 230, 12, 137, 232, 121, 125, 187, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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