Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e3b1fc76d737bafb486161eda34370f3e0f9d99ae471c8f5a2f4927ec3939bc3

Tx prefix hash: ab2ea123f2c3bf781aa1e935ccadd98c8361826caff4762ff0ef0d06221a2c19
Tx public key: aeccf0a2b89732b0c21f5556af8cc9db3b6b4caa43c52f4213e827a4dd0d1ca4
Timestamp: 1714250398 Timestamp [UCT]: 2024-04-27 20:39:58 Age [y:d:h:m:s]: 00:350:04:15:06
Block: 1009887 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0811 kB
Tx version: 2 No of confirmations: 250325 RingCT/type: yes/0
Extra: 01aeccf0a2b89732b0c21f5556af8cc9db3b6b4caa43c52f4213e827a4dd0d1ca4

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bf7bd30b041b533a287a595b2ceee41fc02dae16ad73410dba8495764d48c336 0.600000000000 1471683 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": 1009897, "vin": [ { "gen": { "height": 1009887 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bf7bd30b041b533a287a595b2ceee41fc02dae16ad73410dba8495764d48c336" } } ], "extra": [ 1, 174, 204, 240, 162, 184, 151, 50, 176, 194, 31, 85, 86, 175, 140, 201, 219, 59, 107, 76, 170, 67, 197, 47, 66, 19, 232, 39, 164, 221, 13, 28, 164 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8