Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e959d4101865162003a2612cbb27ed6b0d0980334390691fdbf73ddae89916f4

Tx prefix hash: 11c4358b2edfa369c0a1c86aa7ee53c5556b6f955d0928906fa25b3e5e5f4717
Tx public key: 3f33165b6ddba7fff6d5c3b996311465fbaec380de85cece3cde03212e530c76
Timestamp: 1683822517 Timestamp [UCT]: 2023-05-11 16:28:37 Age [y:d:h:m:s]: 01:334:11:09:13
Block: 757878 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 500278 RingCT/type: yes/0
Extra: 013f33165b6ddba7fff6d5c3b996311465fbaec380de85cece3cde03212e530c7602110000000475e3f0e9000000000000000000

1 output(s) for total of 1.891628146000 dcy

stealth address amount amount idx
00: eb3dca84d5afaa08936445941be295d582dfe2cccc993c01f8ba93f71214bc1f 1.891628146000 1206339 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": 757888, "vin": [ { "gen": { "height": 757878 } } ], "vout": [ { "amount": 1891628146, "target": { "key": "eb3dca84d5afaa08936445941be295d582dfe2cccc993c01f8ba93f71214bc1f" } } ], "extra": [ 1, 63, 51, 22, 91, 109, 219, 167, 255, 246, 213, 195, 185, 150, 49, 20, 101, 251, 174, 195, 128, 222, 133, 206, 206, 60, 222, 3, 33, 46, 83, 12, 118, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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