Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b1af0240bc6bb9f7eadbf88b1d19b9d0a33a28ea5cf4c7cc463281c2eeaf3102

Tx prefix hash: 4a59a3c452760af75666112279c45024e6dba0c77dd04132a0db772c63a6b913
Tx public key: 3c07a4dbb118f673d9c908bd8afd7ba9c5e849526680b0d442f9c93cf3042f83
Timestamp: 1757167427 Timestamp [UCT]: 2025-09-06 14:03:47 Age [y:d:h:m:s]: 00:107:06:16:44
Block: 1362667 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 76715 RingCT/type: yes/0
Extra: 013c07a4dbb118f673d9c908bd8afd7ba9c5e849526680b0d442f9c93cf3042f83021100000008ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e8dc5b0214956620d12584ed6a224ce512fa21e7d22b9174fbd8434b2e29bec1 0.600000000000 1850698 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": 1362677, "vin": [ { "gen": { "height": 1362667 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e8dc5b0214956620d12584ed6a224ce512fa21e7d22b9174fbd8434b2e29bec1" } } ], "extra": [ 1, 60, 7, 164, 219, 177, 24, 246, 115, 217, 201, 8, 189, 138, 253, 123, 169, 197, 232, 73, 82, 102, 128, 176, 212, 66, 249, 201, 60, 243, 4, 47, 131, 2, 17, 0, 0, 0, 8, 173, 121, 72, 208, 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