Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fa16c940f42a64954f14699e468f693cd842d5a0eda24fd8204a00cc0f38ffad

Tx prefix hash: 85e4b8d7ccd405f5cd8ae2ba9f9b34f84ad5deccb02b9f16fb35e497e9e27c9d
Tx public key: 2cb8823e7ecd8e894028611fdfc78d1f1ec2dafe6fdf7c26e4a55b9bea2b3225
Timestamp: 1713756975 Timestamp [UCT]: 2024-04-22 03:36:15 Age [y:d:h:m:s]: 01:025:17:30:17
Block: 1005793 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 279340 RingCT/type: yes/0
Extra: 012cb8823e7ecd8e894028611fdfc78d1f1ec2dafe6fdf7c26e4a55b9bea2b322502110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 969329baf40e7933b32c301d8105f7da08c86763940535c2f00f74530b67e482 0.600000000000 1466599 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": 1005803, "vin": [ { "gen": { "height": 1005793 } } ], "vout": [ { "amount": 600000000, "target": { "key": "969329baf40e7933b32c301d8105f7da08c86763940535c2f00f74530b67e482" } } ], "extra": [ 1, 44, 184, 130, 62, 126, 205, 142, 137, 64, 40, 97, 31, 223, 199, 141, 31, 30, 194, 218, 254, 111, 223, 124, 38, 228, 165, 91, 155, 234, 43, 50, 37, 2, 17, 0, 0, 0, 3, 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