Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8e19fabcb358c007b4ae7c080262dbc31f0cc277910f69d6769fa819f2d6a1b5

Tx prefix hash: 685911c6a5f0c83b19fdb342a18d7608aa1f2f622a70f1ae162069520802f805
Tx public key: 8028ca1ce81e5c60b2ab31cb26739008fde4c90b1fe76d9bf40fe690f7eb9422
Timestamp: 1732258323 Timestamp [UCT]: 2024-11-22 06:52:03 Age [y:d:h:m:s]: 00:001:18:56:57
Block: 1159084 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1293 RingCT/type: yes/0
Extra: 018028ca1ce81e5c60b2ab31cb26739008fde4c90b1fe76d9bf40fe690f7eb9422021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1eb7b9a76d79a4d71b1dbd6b16ebcf64ccf06f2be59a9f1c89c2fe9ab77ec884 0.600000000000 1644715 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": 1159094, "vin": [ { "gen": { "height": 1159084 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1eb7b9a76d79a4d71b1dbd6b16ebcf64ccf06f2be59a9f1c89c2fe9ab77ec884" } } ], "extra": [ 1, 128, 40, 202, 28, 232, 30, 92, 96, 178, 171, 49, 203, 38, 115, 144, 8, 253, 228, 201, 11, 31, 231, 109, 155, 244, 15, 230, 144, 247, 235, 148, 34, 2, 17, 0, 0, 0, 7, 0, 127, 151, 138, 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