Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7898e0f27d2d7dc3951ed38545809c99bbc8d871427d02205e0e3c2ee5480ec7

Tx prefix hash: 4dbdb6a0ceeab3b17f8134fea1addffdeb106cc265d5a52f3293fd9411b4686a
Tx public key: 579b60e59de405abf17e3cd79d05ca7187162524375dda1c7f9bef2b36da2a4f
Timestamp: 1737813584 Timestamp [UCT]: 2025-01-25 13:59:44 Age [y:d:h:m:s]: 00:145:21:26:30
Block: 1205043 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103970 RingCT/type: yes/0
Extra: 01579b60e59de405abf17e3cd79d05ca7187162524375dda1c7f9bef2b36da2a4f021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b1c6c47c52753eb18bb87ca2e0615ea8a9ff6724125e8e26fcc3496847a9c134 0.600000000000 1691740 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": 1205053, "vin": [ { "gen": { "height": 1205043 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b1c6c47c52753eb18bb87ca2e0615ea8a9ff6724125e8e26fcc3496847a9c134" } } ], "extra": [ 1, 87, 155, 96, 229, 157, 228, 5, 171, 241, 126, 60, 215, 157, 5, 202, 113, 135, 22, 37, 36, 55, 93, 218, 28, 127, 155, 239, 43, 54, 218, 42, 79, 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