Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ed3d79f9a7a4cb5cb932ff095aa227ace55da65beaf1d0a8d5671f3ad22f1682

Tx prefix hash: dd480937583c036910b45b12a84f090a42dd72108f692790140cbf82f345084a
Tx public key: ae832a396f503eae144a2ddf9cca8107f10a9f14fb12d6ccd3672b60e81555ae
Timestamp: 1578003829 Timestamp [UCT]: 2020-01-02 22:23:49 Age [y:d:h:m:s]: 04:308:14:15:10
Block: 37458 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1109625 RingCT/type: yes/0
Extra: 01ae832a396f503eae144a2ddf9cca8107f10a9f14fb12d6ccd3672b60e81555ae021100000008d81c26c0000000000000000000

1 output(s) for total of 461.197503548000 dcy

stealth address amount amount idx
00: f26c5691a209a48b378d7eb6d3e7c71bc26b89f924680f9a0face1f5cb26372e 461.197503548000 63594 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": 37468, "vin": [ { "gen": { "height": 37458 } } ], "vout": [ { "amount": 461197503548, "target": { "key": "f26c5691a209a48b378d7eb6d3e7c71bc26b89f924680f9a0face1f5cb26372e" } } ], "extra": [ 1, 174, 131, 42, 57, 111, 80, 62, 174, 20, 74, 45, 223, 156, 202, 129, 7, 241, 10, 159, 20, 251, 18, 214, 204, 211, 103, 43, 96, 232, 21, 85, 174, 2, 17, 0, 0, 0, 8, 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