Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8f2590bd5442c714372c36f531960c0df5aab10b286667ec15008fe6007a1636

Tx prefix hash: 56a61f6f27ecf38890082013359b32b20235a5dddd214d392aa33ff719c2d208
Tx public key: a8dfc5d7c55ea0cfee3d4cf6b53aa3ee9ad4992973d21816fd118684ab71f599
Timestamp: 1734676175 Timestamp [UCT]: 2024-12-20 06:29:35 Age [y:d:h:m:s]: 00:101:00:03:06
Block: 1179142 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 71932 RingCT/type: yes/0
Extra: 01a8dfc5d7c55ea0cfee3d4cf6b53aa3ee9ad4992973d21816fd118684ab71f5990211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0a1b07886dee625306491e5e9a6b356d001b1e98a319fbc011c9b6307f6d7a45 0.600000000000 1665533 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": 1179152, "vin": [ { "gen": { "height": 1179142 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0a1b07886dee625306491e5e9a6b356d001b1e98a319fbc011c9b6307f6d7a45" } } ], "extra": [ 1, 168, 223, 197, 215, 197, 94, 160, 207, 238, 61, 76, 246, 181, 58, 163, 238, 154, 212, 153, 41, 115, 210, 24, 22, 253, 17, 134, 132, 171, 113, 245, 153, 2, 17, 0, 0, 0, 5, 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