Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aa514fc69eea0c0c3f6c232a2950dc75be929a30be1fedc68a6af582463e4058

Tx prefix hash: fe64741969d574a3a39165f7c4c552acb51efd1bfb60c83088bb507acdbe3500
Tx public key: f694216ab54f58b6451a5d53458a856e74a997aab095f5d47ae754e550705df0
Timestamp: 1704866628 Timestamp [UCT]: 2024-01-10 06:03:48 Age [y:d:h:m:s]: 01:328:10:24:37
Block: 932073 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 493602 RingCT/type: yes/0
Extra: 01f694216ab54f58b6451a5d53458a856e74a997aab095f5d47ae754e550705df00211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4ffad1260d9d4b8181b17cfd8021b3d60a650362c6cbde09c9b35dd8c7f48281 0.600000000000 1389991 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": 932083, "vin": [ { "gen": { "height": 932073 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4ffad1260d9d4b8181b17cfd8021b3d60a650362c6cbde09c9b35dd8c7f48281" } } ], "extra": [ 1, 246, 148, 33, 106, 181, 79, 88, 182, 69, 26, 93, 83, 69, 138, 133, 110, 116, 169, 151, 170, 176, 149, 245, 212, 122, 231, 84, 229, 80, 112, 93, 240, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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