Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 80c9113d09bdfbf7a25f492283a28e0fbf81427b798b02ec731872f27776685e

Tx prefix hash: 911cc538ed316181cb8581548a28216a72817a7e2790835b8ffaca3e7a9ef15d
Tx public key: ab1a3658f59c4d3e17bdea4dee76f60ada309108e29015a140d9a95bf0d12c6c
Timestamp: 1579147835 Timestamp [UCT]: 2020-01-16 04:10:35 Age [y:d:h:m:s]: 05:117:12:55:03
Block: 46521 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1234201 RingCT/type: yes/0
Extra: 01ab1a3658f59c4d3e17bdea4dee76f60ada309108e29015a140d9a95bf0d12c6c021100000037dcee4b4d000000000000000000

1 output(s) for total of 430.385323687000 dcy

stealth address amount amount idx
00: 87a10a208f52ff0a9b0ec0fd07226b2146cb49e943cfda3069787ccfb923193d 430.385323687000 85617 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": 46531, "vin": [ { "gen": { "height": 46521 } } ], "vout": [ { "amount": 430385323687, "target": { "key": "87a10a208f52ff0a9b0ec0fd07226b2146cb49e943cfda3069787ccfb923193d" } } ], "extra": [ 1, 171, 26, 54, 88, 245, 156, 77, 62, 23, 189, 234, 77, 238, 118, 246, 10, 218, 48, 145, 8, 226, 144, 21, 161, 64, 217, 169, 91, 240, 209, 44, 108, 2, 17, 0, 0, 0, 55, 220, 238, 75, 77, 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