Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 018a949a73320dd2892e97a92f7777acbc43c4fc1983262a38f678dcd7f95bad

Tx prefix hash: 0fc07c0fea456d0849b5a7e7ddcef9c77935136579a1c772236e4e96fc052d8b
Tx public key: 6050ab9e63f67fac55a3ffcb18c531d36ccc2bee1f75b8f81a62dcb5097a6c0d
Timestamp: 1694415103 Timestamp [UCT]: 2023-09-11 06:51:43 Age [y:d:h:m:s]: 01:067:08:01:28
Block: 845623 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 309409 RingCT/type: yes/0
Extra: 016050ab9e63f67fac55a3ffcb18c531d36ccc2bee1f75b8f81a62dcb5097a6c0d0211000000184b8f5122000000000000000000

1 output(s) for total of 0.968500901000 dcy

stealth address amount amount idx
00: c2969e276b95139a5b1ea4fc06b9c7c5b056bfd31d4f166dca4d8a9dec259a2f 0.968500901000 1299029 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": 845633, "vin": [ { "gen": { "height": 845623 } } ], "vout": [ { "amount": 968500901, "target": { "key": "c2969e276b95139a5b1ea4fc06b9c7c5b056bfd31d4f166dca4d8a9dec259a2f" } } ], "extra": [ 1, 96, 80, 171, 158, 99, 246, 127, 172, 85, 163, 255, 203, 24, 197, 49, 211, 108, 204, 43, 238, 31, 117, 184, 248, 26, 98, 220, 181, 9, 122, 108, 13, 2, 17, 0, 0, 0, 24, 75, 143, 81, 34, 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