Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8b01be5946ca7bd842d5c8374ee90b2b800e6a8c7d978dd91bdfd7b5aa4de208

Tx prefix hash: 155188354cc0a63177df1db88a4f90cf0dfe048c45781d995fc057e55f02952b
Tx public key: 1aaf98f5204e2e5129b86138042256f56425d9f197d379af8679d60b365beb3f
Timestamp: 1725101155 Timestamp [UCT]: 2024-08-31 10:45:55 Age [y:d:h:m:s]: 00:084:21:07:11
Block: 1099847 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 60703 RingCT/type: yes/0
Extra: 011aaf98f5204e2e5129b86138042256f56425d9f197d379af8679d60b365beb3f02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e1b6f8efecf1cd709afab41aa9488892fe3a15557d2a6c25c7a4f031feb96569 0.600000000000 1575816 of 15

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": 1099857, "vin": [ { "gen": { "height": 1099847 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e1b6f8efecf1cd709afab41aa9488892fe3a15557d2a6c25c7a4f031feb96569" } } ], "extra": [ 1, 26, 175, 152, 245, 32, 78, 46, 81, 41, 184, 97, 56, 4, 34, 86, 245, 100, 37, 217, 241, 151, 211, 121, 175, 134, 121, 214, 11, 54, 91, 235, 63, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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