Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8fbe17973a96529207bd2b61d133a251826b78b445068152d7f2aae681769ed8

Tx prefix hash: 11b0a76cef6bd5294633e94e67db8b236e61f5735c836ef1957824224ec9191a
Tx public key: 601e4f4f8c7687ea4cf2b6a6bd9c9fd58652cfa7ba5a32a215d0e8bb5049e1bb
Timestamp: 1648513613 Timestamp [UCT]: 2022-03-29 00:26:53 Age [y:d:h:m:s]: 02:225:00:25:41
Block: 468556 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 680338 RingCT/type: yes/0
Extra: 01601e4f4f8c7687ea4cf2b6a6bd9c9fd58652cfa7ba5a32a215d0e8bb5049e1bb02110000001e4a0f5013000000000000000000

1 output(s) for total of 17.198070176000 dcy

stealth address amount amount idx
00: eae8d52e88f0c1d002071428463dba31b4a2bbe02d7f167bb33510d2622c02c1 17.198070176000 887296 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": 468566, "vin": [ { "gen": { "height": 468556 } } ], "vout": [ { "amount": 17198070176, "target": { "key": "eae8d52e88f0c1d002071428463dba31b4a2bbe02d7f167bb33510d2622c02c1" } } ], "extra": [ 1, 96, 30, 79, 79, 140, 118, 135, 234, 76, 242, 182, 166, 189, 156, 159, 213, 134, 82, 207, 167, 186, 90, 50, 162, 21, 208, 232, 187, 80, 73, 225, 187, 2, 17, 0, 0, 0, 30, 74, 15, 80, 19, 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