Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cdc8fdb6c3e02ed3ccfc95dc5467ef2e6df00ce69b7d77bc103e3deb66543525

Tx prefix hash: 607d7d05730e0a07ceb018d89795cd3d7452013d07e20d52e6ae3d5529b77974
Tx public key: fad96d5252e04840f0e313cff14a1aab5b4ac1d51b00b8da2e3d7b1a1aaabcf8
Timestamp: 1699950065 Timestamp [UCT]: 2023-11-14 08:21:05 Age [y:d:h:m:s]: 01:124:03:49:12
Block: 891335 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 349929 RingCT/type: yes/0
Extra: 01fad96d5252e04840f0e313cff14a1aab5b4ac1d51b00b8da2e3d7b1a1aaabcf8021100000002e6d27f9c000000000000000000

1 output(s) for total of 0.683340452000 dcy

stealth address amount amount idx
00: 0e55dce3834d6c18a487727d41e35010bb75d2285f8bb32f64baf056f6409ca0 0.683340452000 1347374 of 0

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": 891345, "vin": [ { "gen": { "height": 891335 } } ], "vout": [ { "amount": 683340452, "target": { "key": "0e55dce3834d6c18a487727d41e35010bb75d2285f8bb32f64baf056f6409ca0" } } ], "extra": [ 1, 250, 217, 109, 82, 82, 224, 72, 64, 240, 227, 19, 207, 241, 74, 26, 171, 91, 74, 193, 213, 27, 0, 184, 218, 46, 61, 123, 26, 26, 170, 188, 248, 2, 17, 0, 0, 0, 2, 230, 210, 127, 156, 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