Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 08f9cd485ed4f677f7cc1ba3fbb94eef8349145407b913263674398d5df8c456

Tx prefix hash: ad0a3d4a51077b1d32495c6afaf64b1d1cad4c0fb8bd586a45062d0498902cca
Tx public key: cac201659c5d658f9b2ce7d9019ab26e2d86204fe96dee5fc1db511cb611f743
Timestamp: 1735922064 Timestamp [UCT]: 2025-01-03 16:34:24 Age [y:d:h:m:s]: 00:310:14:57:33
Block: 1189437 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 219499 RingCT/type: yes/0
Extra: 01cac201659c5d658f9b2ce7d9019ab26e2d86204fe96dee5fc1db511cb611f7430211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1ad74a1e0905adf0e946972c2e68aead12b484decc73d4de962fd2e548b7d4f4 0.600000000000 1675946 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": 1189447, "vin": [ { "gen": { "height": 1189437 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1ad74a1e0905adf0e946972c2e68aead12b484decc73d4de962fd2e548b7d4f4" } } ], "extra": [ 1, 202, 194, 1, 101, 156, 93, 101, 143, 155, 44, 231, 217, 1, 154, 178, 110, 45, 134, 32, 79, 233, 109, 238, 95, 193, 219, 81, 28, 182, 17, 247, 67, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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