Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6ac2d89595d28989d727b04fdc1f00599a684fc1313cf9ae0f2a2c9fdbb21edc

Tx prefix hash: cc740c965a4ed3fd211176ec1b4e37b2738da7d95ed896e9a533e707a9318b0e
Tx public key: 5a196527a9d61efcaa0b4e7cbc811fc11a0a815b8ad725a1b807a3a8f3e9d2cd
Timestamp: 1711702236 Timestamp [UCT]: 2024-03-29 08:50:36 Age [y:d:h:m:s]: 01:017:12:04:51
Block: 988776 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 273469 RingCT/type: yes/0
Extra: 015a196527a9d61efcaa0b4e7cbc811fc11a0a815b8ad725a1b807a3a8f3e9d2cd0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d1704772d80e15096b62cf6924ce6a2403457a485c20be714fc83a7a6ffe63ca 0.600000000000 1449061 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": 988786, "vin": [ { "gen": { "height": 988776 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d1704772d80e15096b62cf6924ce6a2403457a485c20be714fc83a7a6ffe63ca" } } ], "extra": [ 1, 90, 25, 101, 39, 169, 214, 30, 252, 170, 11, 78, 124, 188, 129, 31, 193, 26, 10, 129, 91, 138, 215, 37, 161, 184, 7, 163, 168, 243, 233, 210, 205, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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