Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 30c4304786ac10189cc587d75f658d2951019a0a4c5b69bb6734af1f7d4f34e9

Tx prefix hash: d23b8877f84e30be8b3605e8561b83e2e3f4e90051066e738a0eaef04ee62970
Tx public key: 904a91d8df1735788e31907ffd719c17dfa499902e0e755a297ff2b5c6971550
Timestamp: 1728718343 Timestamp [UCT]: 2024-10-12 07:32:23 Age [y:d:h:m:s]: 00:170:01:32:10
Block: 1129834 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 121328 RingCT/type: yes/0
Extra: 01904a91d8df1735788e31907ffd719c17dfa499902e0e755a297ff2b5c697155002110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8339a06382810bebdce6d37c9c8a49cfa4359f7d2dfda40b13c1d63f03224fe9 0.600000000000 1612703 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": 1129844, "vin": [ { "gen": { "height": 1129834 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8339a06382810bebdce6d37c9c8a49cfa4359f7d2dfda40b13c1d63f03224fe9" } } ], "extra": [ 1, 144, 74, 145, 216, 223, 23, 53, 120, 142, 49, 144, 127, 253, 113, 156, 23, 223, 164, 153, 144, 46, 14, 117, 90, 41, 127, 242, 181, 198, 151, 21, 80, 2, 17, 0, 0, 0, 1, 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