Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e6a57240141569f277b3510402129c0e851b839c8dbd879a3846c80d0c8c00ca

Tx prefix hash: ddfd1fff2f6ac7bc8b90b07b7b392cac49b621ba8807f76eaeeb515bb43f44bb
Tx public key: dfefa1585eb5170b7489e2e708a97a9bb84b82b5f3a94a498192a3e31efe50af
Timestamp: 1697300816 Timestamp [UCT]: 2023-10-14 16:26:56 Age [y:d:h:m:s]: 01:185:21:35:55
Block: 869571 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 393893 RingCT/type: yes/0
Extra: 01dfefa1585eb5170b7489e2e708a97a9bb84b82b5f3a94a498192a3e31efe50af021100000015faf35c9c000000000000000000

1 output(s) for total of 0.806771093000 dcy

stealth address amount amount idx
00: fb18dad6198a12e20bbbffe52e59ad365f1e10933e108855f9c231faa507b787 0.806771093000 1324420 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": 869581, "vin": [ { "gen": { "height": 869571 } } ], "vout": [ { "amount": 806771093, "target": { "key": "fb18dad6198a12e20bbbffe52e59ad365f1e10933e108855f9c231faa507b787" } } ], "extra": [ 1, 223, 239, 161, 88, 94, 181, 23, 11, 116, 137, 226, 231, 8, 169, 122, 155, 184, 75, 130, 181, 243, 169, 74, 73, 129, 146, 163, 227, 30, 254, 80, 175, 2, 17, 0, 0, 0, 21, 250, 243, 92, 156, 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