Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ec53a3c4111116228d0697a6ae7f6c45e41ac226cde8eda9eb6fafbf4145b1fa

Tx prefix hash: db3feee1a81cb0e88d7804005ea514eb11965ac690c9196bcffc3af56ade50f2
Tx public key: 85c2aa5d7443fe8b1a9366ad49089ad4c8b773d7dbc632cc0986d6827d3567cb
Timestamp: 1731957099 Timestamp [UCT]: 2024-11-18 19:11:39 Age [y:d:h:m:s]: 00:136:06:46:04
Block: 1156583 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 97217 RingCT/type: yes/0
Extra: 0185c2aa5d7443fe8b1a9366ad49089ad4c8b773d7dbc632cc0986d6827d3567cb021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bdf8ca2f1cbd475db539e536282045854a4c57241ee962d1279f718f517caa55 0.600000000000 1642206 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": 1156593, "vin": [ { "gen": { "height": 1156583 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bdf8ca2f1cbd475db539e536282045854a4c57241ee962d1279f718f517caa55" } } ], "extra": [ 1, 133, 194, 170, 93, 116, 67, 254, 139, 26, 147, 102, 173, 73, 8, 154, 212, 200, 183, 115, 215, 219, 198, 50, 204, 9, 134, 214, 130, 125, 53, 103, 203, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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