Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 58a8f05e5e9393488a010ee198d342ec168f8510e6f8af93c3c0f0a435a2b7ee

Tx prefix hash: 8c4d191cfc3beb8b20b1fbf67528b41a890bf28ad0e087457837574a0be1cc4a
Tx public key: 3cec029f62fdfca2957d3a77a1d2b2e016307577585508751cf25924333b2c22
Timestamp: 1754667893 Timestamp [UCT]: 2025-08-08 15:44:53 Age [y:d:h:m:s]: 00:150:08:03:22
Block: 1342909 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106625 RingCT/type: yes/0
Extra: 013cec029f62fdfca2957d3a77a1d2b2e016307577585508751cf25924333b2c22021100000002e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6e3babc4d728fd10a2f1f7817943421f81283d098882723ab71bd6a8ec72be79 0.600000000000 1830744 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": 1342919, "vin": [ { "gen": { "height": 1342909 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6e3babc4d728fd10a2f1f7817943421f81283d098882723ab71bd6a8ec72be79" } } ], "extra": [ 1, 60, 236, 2, 159, 98, 253, 252, 162, 149, 125, 58, 119, 161, 210, 178, 224, 22, 48, 117, 119, 88, 85, 8, 117, 28, 242, 89, 36, 51, 59, 44, 34, 2, 17, 0, 0, 0, 2, 228, 220, 144, 9, 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