Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c7be0a2711a0e34fc97e9df0b100a7e5a052940edc655c4e2491dac6beec4427

Tx prefix hash: f60a01ef373d738992eaf005b43bd5c5c64b46a3933f5e4dacc7f0726dfc459b
Tx public key: f808304a8e0e83afc3715fdcf29d643b5441e010106fc4200231363a8a2b6c0a
Timestamp: 1720752176 Timestamp [UCT]: 2024-07-12 02:42:56 Age [y:d:h:m:s]: 00:184:07:30:06
Block: 1063802 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 131872 RingCT/type: yes/0
Extra: 01f808304a8e0e83afc3715fdcf29d643b5441e010106fc4200231363a8a2b6c0a02110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7ab80e82e276a88df18112b14868b061fe233e84ba7d3550cb0876d836c16c65 0.600000000000 1534319 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": 1063812, "vin": [ { "gen": { "height": 1063802 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7ab80e82e276a88df18112b14868b061fe233e84ba7d3550cb0876d836c16c65" } } ], "extra": [ 1, 248, 8, 48, 74, 142, 14, 131, 175, 195, 113, 95, 220, 242, 157, 100, 59, 84, 65, 224, 16, 16, 111, 196, 32, 2, 49, 54, 58, 138, 43, 108, 10, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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