Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 07ea10267a51a798b7c18a7465609b8732441afd5376619524a0dd5bcc26d1b2

Tx prefix hash: 64e423189241fb8941a66b133d0f46a9f38634126af23490688a619339e76048
Tx public key: b61a8c76c0d9f5c385e8a8c1c062e0fbe28984e9d04f16b7b75aa80e83976c34
Timestamp: 1735731900 Timestamp [UCT]: 2025-01-01 11:45:00 Age [y:d:h:m:s]: 00:163:17:19:30
Block: 1187844 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 116769 RingCT/type: yes/0
Extra: 01b61a8c76c0d9f5c385e8a8c1c062e0fbe28984e9d04f16b7b75aa80e83976c340211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1160f3a143701c255974083cf105319ccf3dced66f03849e6370114af43547b9 0.600000000000 1674341 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": 1187854, "vin": [ { "gen": { "height": 1187844 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1160f3a143701c255974083cf105319ccf3dced66f03849e6370114af43547b9" } } ], "extra": [ 1, 182, 26, 140, 118, 192, 217, 245, 195, 133, 232, 168, 193, 192, 98, 224, 251, 226, 137, 132, 233, 208, 79, 22, 183, 183, 90, 168, 14, 131, 151, 108, 52, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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