Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd61ea5b84c4737df5fd432517eb94170e2ec6b7d8f614c2379f78f3f2c6eec4

Tx prefix hash: 710493e6386a887f643434d12c24777cc60146c9b66b9a6af70c1eaf6876a4ba
Tx public key: 2748202605b3ab6194b8a40e9694c6050b7fc2510b0c0f38b4b9d86a22c09ac3
Timestamp: 1710169228 Timestamp [UCT]: 2024-03-11 15:00:28 Age [y:d:h:m:s]: 01:025:20:44:17
Block: 976068 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 279465 RingCT/type: yes/0
Extra: 012748202605b3ab6194b8a40e9694c6050b7fc2510b0c0f38b4b9d86a22c09ac302110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cb9abc8adefb08a9bc15c22e27863de1946e233097067b4cd10826483c737cd7 0.600000000000 1436055 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": 976078, "vin": [ { "gen": { "height": 976068 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cb9abc8adefb08a9bc15c22e27863de1946e233097067b4cd10826483c737cd7" } } ], "extra": [ 1, 39, 72, 32, 38, 5, 179, 171, 97, 148, 184, 164, 14, 150, 148, 198, 5, 11, 127, 194, 81, 11, 12, 15, 56, 180, 185, 216, 106, 34, 192, 154, 195, 2, 17, 0, 0, 0, 1, 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