Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a455c7f1eb844be0a7db29519e186ca2dd8da9cb547deed475d30a541084bc30

Tx prefix hash: 98069f83c4f82b4c8ab96c26b38f16d0963c17d4d15d9deb2d8520452b3987ff
Tx public key: 2dc0b9947738f7c5e53e7e21e8b30f50224679558667c7b1c4e0e851d2eb6be2
Timestamp: 1713841816 Timestamp [UCT]: 2024-04-23 03:10:16 Age [y:d:h:m:s]: 01:028:02:44:02
Block: 1006499 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 281063 RingCT/type: yes/0
Extra: 012dc0b9947738f7c5e53e7e21e8b30f50224679558667c7b1c4e0e851d2eb6be20211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 872e40237456ac056cd21a4093208a4b3c581a4fdedf4c215918dc4cb58f154b 0.600000000000 1467549 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": 1006509, "vin": [ { "gen": { "height": 1006499 } } ], "vout": [ { "amount": 600000000, "target": { "key": "872e40237456ac056cd21a4093208a4b3c581a4fdedf4c215918dc4cb58f154b" } } ], "extra": [ 1, 45, 192, 185, 148, 119, 56, 247, 197, 229, 62, 126, 33, 232, 179, 15, 80, 34, 70, 121, 85, 134, 103, 199, 177, 196, 224, 232, 81, 210, 235, 107, 226, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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