Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c33501eeb78f7e5b7c8f4b94d7b972c99408831fa889e010de8b5fffdf822b4b

Tx prefix hash: bf8e7613560d8570abed0fb42339dbd4bb9b9f79f391dfa8059793d64c0fc4ca
Tx public key: ccc2b0f899b3e13fbdf5cca2a49effb0cd51435cbbc32dfb4d4cccdd365230b8
Timestamp: 1719330470 Timestamp [UCT]: 2024-06-25 15:47:50 Age [y:d:h:m:s]: 00:242:22:02:45
Block: 1051995 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 173540 RingCT/type: yes/0
Extra: 01ccc2b0f899b3e13fbdf5cca2a49effb0cd51435cbbc32dfb4d4cccdd365230b80211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b843b3157ee44b7a9a1ec2d6ede05847bf8d0f45e2447e71b258a6b26280b83e 0.600000000000 1522316 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": 1052005, "vin": [ { "gen": { "height": 1051995 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b843b3157ee44b7a9a1ec2d6ede05847bf8d0f45e2447e71b258a6b26280b83e" } } ], "extra": [ 1, 204, 194, 176, 248, 153, 179, 225, 63, 189, 245, 204, 162, 164, 158, 255, 176, 205, 81, 67, 92, 187, 195, 45, 251, 77, 76, 204, 221, 54, 82, 48, 184, 2, 17, 0, 0, 0, 6, 122, 156, 244, 199, 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