Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d6761821067ac761d4e9c4e8daf673e5ed7de2daf67d555fb3bf542c0e2fa6b5

Tx prefix hash: f892953d4851894524a22de92cf323972e76134573e31354c76bf98ba3828e8e
Tx public key: 5cbe4dc874d8a60f387b93eec76c71098c71e3b3a2665f4284a7c3920479d4ea
Timestamp: 1711296472 Timestamp [UCT]: 2024-03-24 16:07:52 Age [y:d:h:m:s]: 01:051:00:40:12
Block: 985419 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 297454 RingCT/type: yes/0
Extra: 015cbe4dc874d8a60f387b93eec76c71098c71e3b3a2665f4284a7c3920479d4ea02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e371328ec65925349ad0ed0da06ece529375e5c343514835f26619dcffa7ccb8 0.600000000000 1445630 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": 985429, "vin": [ { "gen": { "height": 985419 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e371328ec65925349ad0ed0da06ece529375e5c343514835f26619dcffa7ccb8" } } ], "extra": [ 1, 92, 190, 77, 200, 116, 216, 166, 15, 56, 123, 147, 238, 199, 108, 113, 9, 140, 113, 227, 179, 162, 102, 95, 66, 132, 167, 195, 146, 4, 121, 212, 234, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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