Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 521e006b8fc93ba8d1e0d40829340b0774084b24d0cd35ecc76ad64d426775b6

Tx prefix hash: 7982d152ab9f96b5c7788703c031e3cc001766153bbcc2205103b24383cde476
Tx public key: 6c39c9aa53c3ddb88ab3f0ef8ff2094f3e094be0aa026c6f04209ac9965c56a0
Timestamp: 1735877897 Timestamp [UCT]: 2025-01-03 04:18:17 Age [y:d:h:m:s]: 00:073:08:33:04
Block: 1189057 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 52226 RingCT/type: yes/0
Extra: 016c39c9aa53c3ddb88ab3f0ef8ff2094f3e094be0aa026c6f04209ac9965c56a0021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 50aed32fdd00a6bd5c1ec3728b113f83acb3a7d4d06245a09707c7da90c51016 0.600000000000 1675562 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": 1189067, "vin": [ { "gen": { "height": 1189057 } } ], "vout": [ { "amount": 600000000, "target": { "key": "50aed32fdd00a6bd5c1ec3728b113f83acb3a7d4d06245a09707c7da90c51016" } } ], "extra": [ 1, 108, 57, 201, 170, 83, 195, 221, 184, 138, 179, 240, 239, 143, 242, 9, 79, 62, 9, 75, 224, 170, 2, 108, 111, 4, 32, 154, 201, 150, 92, 86, 160, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 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