Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a0903f6666d7300a823775dabd4ca3b539e74585ad740ad0d44ceea812c6c7b1

Tx prefix hash: 1c75fafbfd7916cb8607414a93ec46d31e203e286ef0d7561533573e2df9a466
Tx public key: 885e3ee960626b8e626c4d6db34a64996ca8d4ae092cb71bc60d33dc7d1b067c
Timestamp: 1582037490 Timestamp [UCT]: 2020-02-18 14:51:30 Age [y:d:h:m:s]: 04:330:19:40:27
Block: 67630 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1128768 RingCT/type: yes/0
Extra: 01885e3ee960626b8e626c4d6db34a64996ca8d4ae092cb71bc60d33dc7d1b067c0211000000038a2ee0d9000000000000000000

1 output(s) for total of 366.365476747000 dcy

stealth address amount amount idx
00: 380159807e2db548ca33d71006b442d563991d4df246db940ec4c62e6778f947 366.365476747000 124529 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": 67640, "vin": [ { "gen": { "height": 67630 } } ], "vout": [ { "amount": 366365476747, "target": { "key": "380159807e2db548ca33d71006b442d563991d4df246db940ec4c62e6778f947" } } ], "extra": [ 1, 136, 94, 62, 233, 96, 98, 107, 142, 98, 108, 77, 109, 179, 74, 100, 153, 108, 168, 212, 174, 9, 44, 183, 27, 198, 13, 51, 220, 125, 27, 6, 124, 2, 17, 0, 0, 0, 3, 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