Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5584ac498b1c28a6ae52ec75ff93241de2fec62d17d9172516acb791dc1751f5

Tx prefix hash: 177a19fd27ebbdee5e2164f07143f976c2060ac82cd08bbf16a100832534a0b4
Tx public key: 04466f8a607557510579dcbf40e930a09c597d2576014052a9cd1ce5e81e69f3
Timestamp: 1586723155 Timestamp [UCT]: 2020-04-12 20:25:55 Age [y:d:h:m:s]: 04:228:14:20:47
Block: 93121 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1068943 RingCT/type: yes/0
Extra: 0104466f8a607557510579dcbf40e930a09c597d2576014052a9cd1ce5e81e69f30211000001328a2ee0d9000000000000000000

1 output(s) for total of 301.628487445000 dcy

stealth address amount amount idx
00: 28cd64bb09e60a8c0236f49ccbd1b4e2c404f3cb316b3ca0d215f17d3aed4693 301.628487445000 165907 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": 93131, "vin": [ { "gen": { "height": 93121 } } ], "vout": [ { "amount": 301628487445, "target": { "key": "28cd64bb09e60a8c0236f49ccbd1b4e2c404f3cb316b3ca0d215f17d3aed4693" } } ], "extra": [ 1, 4, 70, 111, 138, 96, 117, 87, 81, 5, 121, 220, 191, 64, 233, 48, 160, 156, 89, 125, 37, 118, 1, 64, 82, 169, 205, 28, 229, 232, 30, 105, 243, 2, 17, 0, 0, 1, 50, 138, 46, 224, 217, 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