Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 30a54142bd262653cd575e164ce4a57e29b81ae3a73cdea8f1867fc191f3500b

Tx prefix hash: 8ccfc57a9d185ab33edac383b354a424dce0495284c7d3a9848f7d4b7961b457
Tx public key: ed8daa0a86158921e6eff6a2a3fe98be8962a2eb02ab9077329bcd52122c1f16
Timestamp: 1681443821 Timestamp [UCT]: 2023-04-14 03:43:41 Age [y:d:h:m:s]: 01:272:13:58:08
Block: 738143 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 456322 RingCT/type: yes/0
Extra: 01ed8daa0a86158921e6eff6a2a3fe98be8962a2eb02ab9077329bcd52122c1f16021100000002b3164c24000000000000000000

1 output(s) for total of 2.199004124000 dcy

stealth address amount amount idx
00: 659017995caef775c24f836a6da9119c58e12c15233bb1e2df1aa0181e3a2bc9 2.199004124000 1184794 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": 738153, "vin": [ { "gen": { "height": 738143 } } ], "vout": [ { "amount": 2199004124, "target": { "key": "659017995caef775c24f836a6da9119c58e12c15233bb1e2df1aa0181e3a2bc9" } } ], "extra": [ 1, 237, 141, 170, 10, 134, 21, 137, 33, 230, 239, 246, 162, 163, 254, 152, 190, 137, 98, 162, 235, 2, 171, 144, 119, 50, 155, 205, 82, 18, 44, 31, 22, 2, 17, 0, 0, 0, 2, 179, 22, 76, 36, 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