Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e33e0706891ae444e16496a8e5a2f3618bf6a19f91d8236042e361c6fd83eb06

Tx prefix hash: 7295585aa25eb5282095f24199f32953b8c428c79c9edac993a4f5c831414835
Tx public key: e7f6c2b3e61469852ee80337b0f6205a40ed2eca69e3b6b43143a37ed2d70fd6
Timestamp: 1704574869 Timestamp [UCT]: 2024-01-06 21:01:09 Age [y:d:h:m:s]: 01:108:13:45:05
Block: 929655 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 338727 RingCT/type: yes/0
Extra: 01e7f6c2b3e61469852ee80337b0f6205a40ed2eca69e3b6b43143a37ed2d70fd602110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ec6c77b66529eda46eb10fb2d40fa27dc370b9c062134f2377ee4930fd4cd1d1 0.600000000000 1387531 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": 929665, "vin": [ { "gen": { "height": 929655 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ec6c77b66529eda46eb10fb2d40fa27dc370b9c062134f2377ee4930fd4cd1d1" } } ], "extra": [ 1, 231, 246, 194, 179, 230, 20, 105, 133, 46, 232, 3, 55, 176, 246, 32, 90, 64, 237, 46, 202, 105, 227, 182, 180, 49, 67, 163, 126, 210, 215, 15, 214, 2, 17, 0, 0, 0, 1, 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