Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 19408ea9aa8d54a93b53e8d1f0f26dc83bbb006e7159a7ea60bf1c1d0ce5b1ef

Tx prefix hash: fd5790425102ce807e608e4c30491489b96cb7e8ae383a8f7809afedccf4dc33
Tx public key: 6d78018d944f30938adfd650f920b11f667dc987d8bc294fb4c639049801e85e
Timestamp: 1580118902 Timestamp [UCT]: 2020-01-27 09:55:02 Age [y:d:h:m:s]: 04:283:19:30:52
Block: 53919 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1092952 RingCT/type: yes/0
Extra: 016d78018d944f30938adfd650f920b11f667dc987d8bc294fb4c639049801e85e021100000001391a8d0e000000000000000000

1 output(s) for total of 406.809502956000 dcy

stealth address amount amount idx
00: 9b917f6158b0944870135d9d031906da9ff4fcb8cc2ad69d15887aa4157c0b5c 406.809502956000 99894 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": 53929, "vin": [ { "gen": { "height": 53919 } } ], "vout": [ { "amount": 406809502956, "target": { "key": "9b917f6158b0944870135d9d031906da9ff4fcb8cc2ad69d15887aa4157c0b5c" } } ], "extra": [ 1, 109, 120, 1, 141, 148, 79, 48, 147, 138, 223, 214, 80, 249, 32, 177, 31, 102, 125, 201, 135, 216, 188, 41, 79, 180, 198, 57, 4, 152, 1, 232, 94, 2, 17, 0, 0, 0, 1, 57, 26, 141, 14, 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