Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5b76575cdda35e3b2af4e0b5660ffa63b32cd76c3f35b61dbc21bd17037f40a0

Tx prefix hash: 4d4fe13cdb794e2bce312a973330cd950b9bad0f03cbbfb53cd1df4900ae3d60
Tx public key: ddf192ed47fdb1cb595db4af9a48b122b9330d6f3b15cc091f0704f790e59157
Timestamp: 1724045256 Timestamp [UCT]: 2024-08-19 05:27:36 Age [y:d:h:m:s]: 00:229:05:03:00
Block: 1091103 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 163680 RingCT/type: yes/0
Extra: 01ddf192ed47fdb1cb595db4af9a48b122b9330d6f3b15cc091f0704f790e59157021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 66f27b8c00974dfbc83c9daaf38eaabc9f41f5390e3632f101331bdc907e7c0e 0.600000000000 1565728 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": 1091113, "vin": [ { "gen": { "height": 1091103 } } ], "vout": [ { "amount": 600000000, "target": { "key": "66f27b8c00974dfbc83c9daaf38eaabc9f41f5390e3632f101331bdc907e7c0e" } } ], "extra": [ 1, 221, 241, 146, 237, 71, 253, 177, 203, 89, 93, 180, 175, 154, 72, 177, 34, 185, 51, 13, 111, 59, 21, 204, 9, 31, 7, 4, 247, 144, 229, 145, 87, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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