Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 38c2d0076b75f8f0e71613e8d40486f97d4cd61ccdc7973562e274255b507f2b

Tx prefix hash: a038aa1293fa4dc6123e9c568c4449922ca2c44d7ceadb1bf4df76368fa4ea5a
Tx public key: 9fb732a26e14926ea84f7e0ed71a660c1c6741c0e22b20c90a0354b3d7d47e3a
Timestamp: 1710760651 Timestamp [UCT]: 2024-03-18 11:17:31 Age [y:d:h:m:s]: 00:255:03:28:46
Block: 980978 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 182649 RingCT/type: yes/0
Extra: 019fb732a26e14926ea84f7e0ed71a660c1c6741c0e22b20c90a0354b3d7d47e3a02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5a43e52bd3732e659f51b765d07dc28c82cd3140a4d7f9eecd6a14317f946857 0.600000000000 1441063 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": 980988, "vin": [ { "gen": { "height": 980978 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5a43e52bd3732e659f51b765d07dc28c82cd3140a4d7f9eecd6a14317f946857" } } ], "extra": [ 1, 159, 183, 50, 162, 110, 20, 146, 110, 168, 79, 126, 14, 215, 26, 102, 12, 28, 103, 65, 192, 226, 43, 32, 201, 10, 3, 84, 179, 215, 212, 126, 58, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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