Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6722a7fe3db8bb299d9e77649c7d4ba553b2793bae8dcab05514d27eabccc5b5

Tx prefix hash: 991229c4c2c8a4d0912a4cc65bc4dd029ec96ea03cab16c1ae07a69ae58aa069
Tx public key: 664d4055ac1586c4c09595443817fa7dc92ae1ee64b071e1bf16acb706701016
Timestamp: 1736525768 Timestamp [UCT]: 2025-01-10 16:16:08 Age [y:d:h:m:s]: 00:088:03:08:10
Block: 1194414 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 62767 RingCT/type: yes/0
Extra: 01664d4055ac1586c4c09595443817fa7dc92ae1ee64b071e1bf16acb70670101602110000000a1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dcf1a1bf77c93af0713a8b21db3d8766e0474f9527f0e92b816cdfa9d94e67a3 0.600000000000 1680985 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": 1194424, "vin": [ { "gen": { "height": 1194414 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dcf1a1bf77c93af0713a8b21db3d8766e0474f9527f0e92b816cdfa9d94e67a3" } } ], "extra": [ 1, 102, 77, 64, 85, 172, 21, 134, 196, 192, 149, 149, 68, 56, 23, 250, 125, 201, 42, 225, 238, 100, 176, 113, 225, 191, 22, 172, 183, 6, 112, 16, 22, 2, 17, 0, 0, 0, 10, 31, 10, 83, 235, 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