Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a31da871b101704ac3368e04e2b691c8f2a8c9f004170bded7388e3b54dd67ee

Tx prefix hash: f0a2adf43e112c5249bef64c78a8ee4639f9085ce415c38312042566bfaf6ab7
Tx public key: 9be83e7807e5a0d6f50825e7e9270e4c93c65b24878a9eab6ec8633bf062bdf4
Timestamp: 1615910317 Timestamp [UCT]: 2021-03-16 15:58:37 Age [y:d:h:m:s]: 03:330:00:20:56
Block: 219864 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 995037 RingCT/type: yes/0
Extra: 019be83e7807e5a0d6f50825e7e9270e4c93c65b24878a9eab6ec8633bf062bdf402110000012e1b1d8a8b000000000000000000

1 output(s) for total of 114.683224221000 dcy

stealth address amount amount idx
00: 56f76462be73fa8fdd821d023da8f075ca4ac8edfc0eac7ff68b7647ea196b2c 114.683224221000 452388 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": 219874, "vin": [ { "gen": { "height": 219864 } } ], "vout": [ { "amount": 114683224221, "target": { "key": "56f76462be73fa8fdd821d023da8f075ca4ac8edfc0eac7ff68b7647ea196b2c" } } ], "extra": [ 1, 155, 232, 62, 120, 7, 229, 160, 214, 245, 8, 37, 231, 233, 39, 14, 76, 147, 198, 91, 36, 135, 138, 158, 171, 110, 200, 99, 59, 240, 98, 189, 244, 2, 17, 0, 0, 1, 46, 27, 29, 138, 139, 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