Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 120b3124c389264a495e018cb949400be21309ce405d16c315543099bffbb83e

Tx prefix hash: 87cb74835ce202553d63c20d067ceabf5ab1419455e0b72db6f24a22c91c5745
Tx public key: 524eed2f6805520dc1a8d5bfa4de943450c25f1daef71d4728bb1170f916da0d
Timestamp: 1584920928 Timestamp [UCT]: 2020-03-22 23:48:48 Age [y:d:h:m:s]: 04:248:12:05:46
Block: 86814 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1074569 RingCT/type: yes/0
Extra: 01524eed2f6805520dc1a8d5bfa4de943450c25f1daef71d4728bb1170f916da0d02110000001f8e8a0ce2000000000000000000

1 output(s) for total of 316.482688880000 dcy

stealth address amount amount idx
00: c2f7da91b41111cf06a7f5d8a60861edc857c0d74e4cd972e30a6afabb24a574 316.482688880000 156626 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": 86824, "vin": [ { "gen": { "height": 86814 } } ], "vout": [ { "amount": 316482688880, "target": { "key": "c2f7da91b41111cf06a7f5d8a60861edc857c0d74e4cd972e30a6afabb24a574" } } ], "extra": [ 1, 82, 78, 237, 47, 104, 5, 82, 13, 193, 168, 213, 191, 164, 222, 148, 52, 80, 194, 95, 29, 174, 247, 29, 71, 40, 187, 17, 112, 249, 22, 218, 13, 2, 17, 0, 0, 0, 31, 142, 138, 12, 226, 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