Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3bb0a5ba7c67c322c6f4c3ae0a342602d1ed86269d7160a159ec0789676b00b7

Tx prefix hash: 14040396bfa76298b910c3b564fc831f97713731abb395cef62db3a9c710d589
Tx public key: 5bd747b5b38bf7e38f3859dd139dd1f2c044d84f537612f5dfa9257a6cab315c
Timestamp: 1721706164 Timestamp [UCT]: 2024-07-23 03:42:44 Age [y:d:h:m:s]: 00:255:13:44:09
Block: 1071688 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 182579 RingCT/type: yes/0
Extra: 015bd747b5b38bf7e38f3859dd139dd1f2c044d84f537612f5dfa9257a6cab315c021100000009e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e16a184de02cd8c24f7ae1190b7bc5c232a2a13e171c305bad95ef0e9ea5c81c 0.600000000000 1544007 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": 1071698, "vin": [ { "gen": { "height": 1071688 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e16a184de02cd8c24f7ae1190b7bc5c232a2a13e171c305bad95ef0e9ea5c81c" } } ], "extra": [ 1, 91, 215, 71, 181, 179, 139, 247, 227, 143, 56, 89, 221, 19, 157, 209, 242, 192, 68, 216, 79, 83, 118, 18, 245, 223, 169, 37, 122, 108, 171, 49, 92, 2, 17, 0, 0, 0, 9, 233, 20, 221, 21, 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