Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 98e42d77ced687b890023407871bc31734f0db6e139e7988f13c3f3887304042

Tx prefix hash: d1cb5e7ac3dee9067ba42eb510fc7a69bbf88262a0242e8fe1e35fe438fa0f02
Tx public key: cf5d801e9a97e75592c0659c881e691191ba72fbcc7771fb361df5af8347b3ea
Timestamp: 1716979569 Timestamp [UCT]: 2024-05-29 10:46:09 Age [y:d:h:m:s]: 00:294:00:45:33
Block: 1032522 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 210152 RingCT/type: yes/0
Extra: 01cf5d801e9a97e75592c0659c881e691191ba72fbcc7771fb361df5af8347b3ea02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fd8f37ad120bf403c8a670359ce49c0c77f7ddbcc893f0c6717618a0a293f1af 0.600000000000 1500975 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": 1032532, "vin": [ { "gen": { "height": 1032522 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fd8f37ad120bf403c8a670359ce49c0c77f7ddbcc893f0c6717618a0a293f1af" } } ], "extra": [ 1, 207, 93, 128, 30, 154, 151, 231, 85, 146, 192, 101, 156, 136, 30, 105, 17, 145, 186, 114, 251, 204, 119, 113, 251, 54, 29, 245, 175, 131, 71, 179, 234, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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