Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9c429b8a139cb2b029d020b1c23662c728f00a4da1e07dd2433b04822471c614

Tx prefix hash: b3f37b4b269439ddb59686573a910bfef322197e223e978ef6f3b872948baf8f
Tx public key: 333402ece3cf8829d84bc793e5224dc216684bb4f0203ee7ea0a62400384821b
Timestamp: 1721165634 Timestamp [UCT]: 2024-07-16 21:33:54 Age [y:d:h:m:s]: 00:194:19:31:32
Block: 1067229 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 139142 RingCT/type: yes/0
Extra: 01333402ece3cf8829d84bc793e5224dc216684bb4f0203ee7ea0a62400384821b02110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 28b5255b8302626ae336ac5f1d4afbe9c4be58472a0f5527acc0ae24e9fd5c35 0.600000000000 1537988 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": 1067239, "vin": [ { "gen": { "height": 1067229 } } ], "vout": [ { "amount": 600000000, "target": { "key": "28b5255b8302626ae336ac5f1d4afbe9c4be58472a0f5527acc0ae24e9fd5c35" } } ], "extra": [ 1, 51, 52, 2, 236, 227, 207, 136, 41, 216, 75, 199, 147, 229, 34, 77, 194, 22, 104, 75, 180, 240, 32, 62, 231, 234, 10, 98, 64, 3, 132, 130, 27, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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