Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f8843bf7f183539527c2f78c87eaac0da83194988560cb9422786097c5dd2059

Tx prefix hash: bb7c2f4663f60d20771de4a61ecb16cc2df65eb8ce348930a535e231f7a2b6ff
Tx public key: 16e15581a5274f012eeac0fe41da056e4b974ce112184b4444c5cc424310daf6
Timestamp: 1634498957 Timestamp [UCT]: 2021-10-17 19:29:17 Age [y:d:h:m:s]: 03:071:23:31:41
Block: 355100 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 829382 RingCT/type: yes/0
Extra: 0116e15581a5274f012eeac0fe41da056e4b974ce112184b4444c5cc424310daf602110000000b8d0de867000000000000000000

1 output(s) for total of 40.870194743000 dcy

stealth address amount amount idx
00: 5bac96bf3cebe6c218739bbd0e642f14f0688d7f5e858978fab08b26d5b5e7fa 40.870194743000 725100 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": 355110, "vin": [ { "gen": { "height": 355100 } } ], "vout": [ { "amount": 40870194743, "target": { "key": "5bac96bf3cebe6c218739bbd0e642f14f0688d7f5e858978fab08b26d5b5e7fa" } } ], "extra": [ 1, 22, 225, 85, 129, 165, 39, 79, 1, 46, 234, 192, 254, 65, 218, 5, 110, 75, 151, 76, 225, 18, 24, 75, 68, 68, 197, 204, 66, 67, 16, 218, 246, 2, 17, 0, 0, 0, 11, 141, 13, 232, 103, 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