Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f51cd990b82075273321bef3806007eb083202fcea0911a6a05428b91c7e8dc5

Tx prefix hash: e728de6fcc94cdeed2a71a69eb26a0466fd68a88436af156aefc20834b58b96b
Tx public key: 2c20eff0467a777a0ae704dc06dbf09e026de445d296c22c7ba8815bce177cfd
Timestamp: 1696681836 Timestamp [UCT]: 2023-10-07 12:30:36 Age [y:d:h:m:s]: 01:104:10:19:42
Block: 864440 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 335867 RingCT/type: yes/0
Extra: 012c20eff0467a777a0ae704dc06dbf09e026de445d296c22c7ba8815bce177cfd02110000000de6d27f9c000000000000000000

1 output(s) for total of 0.838979732000 dcy

stealth address amount amount idx
00: 9c6db11a4d350ff0da06cdb795c8181809b19e51f74fb22447ec4d0bc8a9efcb 0.838979732000 1318954 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": 864450, "vin": [ { "gen": { "height": 864440 } } ], "vout": [ { "amount": 838979732, "target": { "key": "9c6db11a4d350ff0da06cdb795c8181809b19e51f74fb22447ec4d0bc8a9efcb" } } ], "extra": [ 1, 44, 32, 239, 240, 70, 122, 119, 122, 10, 231, 4, 220, 6, 219, 240, 158, 2, 109, 228, 69, 210, 150, 194, 44, 123, 168, 129, 91, 206, 23, 124, 253, 2, 17, 0, 0, 0, 13, 230, 210, 127, 156, 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