Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9d6773e8e8469e6acff7ccb5eedc5d324a66e74db7967a8bc9e0a28469919633

Tx prefix hash: 337b38010db8460318452efb8f9f8841f95224c85fbd69d4bd84e21aa5556a77
Tx public key: 3e7871ebe74d1b435a3beb5fa4c12fecb551657b40f39ed871a9d7892d46babe
Timestamp: 1699867631 Timestamp [UCT]: 2023-11-13 09:27:11 Age [y:d:h:m:s]: 01:182:08:27:52
Block: 890656 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 391536 RingCT/type: yes/0
Extra: 013e7871ebe74d1b435a3beb5fa4c12fecb551657b40f39ed871a9d7892d46babe021100000004faf35c9c000000000000000000

1 output(s) for total of 0.686889599000 dcy

stealth address amount amount idx
00: 80b2ef7238d3e79ed8d1df8dbca4a15260d5a8ddb8355916e15aa451016e9413 0.686889599000 1346685 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": 890666, "vin": [ { "gen": { "height": 890656 } } ], "vout": [ { "amount": 686889599, "target": { "key": "80b2ef7238d3e79ed8d1df8dbca4a15260d5a8ddb8355916e15aa451016e9413" } } ], "extra": [ 1, 62, 120, 113, 235, 231, 77, 27, 67, 90, 59, 235, 95, 164, 193, 47, 236, 181, 81, 101, 123, 64, 243, 158, 216, 113, 169, 215, 137, 45, 70, 186, 190, 2, 17, 0, 0, 0, 4, 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