Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b94d214b7852e00975ae2dcb2ed5efbe270af93564e534aff217af41987b7022

Tx prefix hash: de9a560beda610bd0fe967e2907613bc277bd5891b4695cb9a6443f6b7f126d9
Tx public key: 79b1e69f09260bd0fd0a1c90d77865cadc0b9c10065f654bbfff26c59e9e3bbd
Timestamp: 1704693375 Timestamp [UCT]: 2024-01-08 05:56:15 Age [y:d:h:m:s]: 01:109:17:52:59
Block: 930631 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 339567 RingCT/type: yes/0
Extra: 0179b1e69f09260bd0fd0a1c90d77865cadc0b9c10065f654bbfff26c59e9e3bbd02110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 09ac45ff944d2f014e251bcd1f9bb80158f950d430b6c63a5e58dee1c8dbef14 0.600000000000 1388517 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": 930641, "vin": [ { "gen": { "height": 930631 } } ], "vout": [ { "amount": 600000000, "target": { "key": "09ac45ff944d2f014e251bcd1f9bb80158f950d430b6c63a5e58dee1c8dbef14" } } ], "extra": [ 1, 121, 177, 230, 159, 9, 38, 11, 208, 253, 10, 28, 144, 215, 120, 101, 202, 220, 11, 156, 16, 6, 95, 101, 75, 191, 255, 38, 197, 158, 158, 59, 189, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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