Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0cf3b737d2d86127e1f6c5eb005e850c9db7e515a7f7f45ab2783a6d5f2fd70b

Tx prefix hash: 9da1e59ecdf8132536a6bc826fbdbfb38f4e81e7a3aa538236dcd16a3bb68d0a
Tx public key: 69331ca534b2b58b7c3e86dd743a5449d2dbcf38f2b68752e9c79d37fa572cc0
Timestamp: 1719529659 Timestamp [UCT]: 2024-06-27 23:07:39 Age [y:d:h:m:s]: 00:270:19:15:20
Block: 1053650 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 193496 RingCT/type: yes/0
Extra: 0169331ca534b2b58b7c3e86dd743a5449d2dbcf38f2b68752e9c79d37fa572cc002110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9148b61b29214fda6b2e5256886d4b72c6e9297eb99bd7f3ddd958c8f2d7c404 0.600000000000 1523997 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": 1053660, "vin": [ { "gen": { "height": 1053650 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9148b61b29214fda6b2e5256886d4b72c6e9297eb99bd7f3ddd958c8f2d7c404" } } ], "extra": [ 1, 105, 51, 28, 165, 52, 178, 181, 139, 124, 62, 134, 221, 116, 58, 84, 73, 210, 219, 207, 56, 242, 182, 135, 82, 233, 199, 157, 55, 250, 87, 44, 192, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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