Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 49e77eb7df10c84785f30dec39714ee15034100510f003d066cee3f9f54d2630

Tx prefix hash: f9e64e397eab84adf4d185462ded0735ece504bb6b63bd6401d64b8c5647072e
Tx public key: 45168ec7806bcf017a7ecb6f8ecfbf961beb58130ea8fdd658d3f3bf9648a4f8
Timestamp: 1580383455 Timestamp [UCT]: 2020-01-30 11:24:15 Age [y:d:h:m:s]: 04:281:01:00:07
Block: 55424 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1091652 RingCT/type: yes/0
Extra: 0145168ec7806bcf017a7ecb6f8ecfbf961beb58130ea8fdd658d3f3bf9648a4f8021100000001bd0f9f9f000000000000000000

1 output(s) for total of 402.122251421000 dcy

stealth address amount amount idx
00: e235bd984136d4ae386d0ad1ebf54ce3d5a172f8f86ec0c11294645dc8dbb5ad 402.122251421000 102294 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": 55434, "vin": [ { "gen": { "height": 55424 } } ], "vout": [ { "amount": 402122251421, "target": { "key": "e235bd984136d4ae386d0ad1ebf54ce3d5a172f8f86ec0c11294645dc8dbb5ad" } } ], "extra": [ 1, 69, 22, 142, 199, 128, 107, 207, 1, 122, 126, 203, 111, 142, 207, 191, 150, 27, 235, 88, 19, 14, 168, 253, 214, 88, 211, 243, 191, 150, 72, 164, 248, 2, 17, 0, 0, 0, 1, 189, 15, 159, 159, 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