Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 738c30f05e7b5de9d61981961905629a4360bab83690bd89a13c86e79166c427

Tx prefix hash: 8ca4419fb152b8c5cece1967171a80f383badd686fa54dec3aaf64b2937f84eb
Tx public key: 0b45fbde2e2a5d7c16b0cae139beb6144ead69c5a921f508242c05e42dd9d634
Timestamp: 1746034551 Timestamp [UCT]: 2025-04-30 17:35:51 Age [y:d:h:m:s]: 00:203:11:49:33
Block: 1272867 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 143165 RingCT/type: yes/0
Extra: 010b45fbde2e2a5d7c16b0cae139beb6144ead69c5a921f508242c05e42dd9d634021100000003d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2ac917fb3bea6154edd0049fe182f4d478115d6610c413ea9b572a9c3594b57f 0.600000000000 1760144 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": 1272877, "vin": [ { "gen": { "height": 1272867 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2ac917fb3bea6154edd0049fe182f4d478115d6610c413ea9b572a9c3594b57f" } } ], "extra": [ 1, 11, 69, 251, 222, 46, 42, 93, 124, 22, 176, 202, 225, 57, 190, 182, 20, 78, 173, 105, 197, 169, 33, 245, 8, 36, 44, 5, 228, 45, 217, 214, 52, 2, 17, 0, 0, 0, 3, 216, 231, 210, 65, 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