Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f74ccd14b446c5de7666a42710061f4ecf70ecf77a1c313a6addcfd5e3df40f5

Tx prefix hash: ba3f47d93b7de9194752f77e8164c25f428af7b636fcadfb97bcd8fec07fdfd1
Tx public key: 683be4bb2d00fdb0a7b274c09bdaeb1d436334f2a72c0708a348beeb4ad41762
Timestamp: 1710156742 Timestamp [UCT]: 2024-03-11 11:32:22 Age [y:d:h:m:s]: 01:066:11:17:14
Block: 975963 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 308508 RingCT/type: yes/0
Extra: 01683be4bb2d00fdb0a7b274c09bdaeb1d436334f2a72c0708a348beeb4ad4176202110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 96cc3b1c58d567744d66bfd3494fbd345c4afd5796dc9a83d6e3101ab68db8f5 0.600000000000 1435942 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": 975973, "vin": [ { "gen": { "height": 975963 } } ], "vout": [ { "amount": 600000000, "target": { "key": "96cc3b1c58d567744d66bfd3494fbd345c4afd5796dc9a83d6e3101ab68db8f5" } } ], "extra": [ 1, 104, 59, 228, 187, 45, 0, 253, 176, 167, 178, 116, 192, 155, 218, 235, 29, 67, 99, 52, 242, 167, 44, 7, 8, 163, 72, 190, 235, 74, 212, 23, 98, 2, 17, 0, 0, 0, 6, 89, 218, 211, 245, 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