Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b9eaa414e633a8dcf02d860e42cb2c7416a084011c5500d3d8795d825c9f78f7

Tx prefix hash: e1e6b2f9b95cd83ab1649e70cefd0fb0b650fb14da0333e2a89e16ebafc5a512
Tx public key: cfd27a630662b5df2241b4a54eb5624ec7652c88d7d97ee8ecb67bb25fe96c1b
Timestamp: 1707354043 Timestamp [UCT]: 2024-02-08 01:00:43 Age [y:d:h:m:s]: 01:058:17:19:57
Block: 952701 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 303016 RingCT/type: yes/0
Extra: 01cfd27a630662b5df2241b4a54eb5624ec7652c88d7d97ee8ecb67bb25fe96c1b0211000000050011055b000000000000000000

1 output(s) for total of 0.600010000000 dcy

stealth address amount amount idx
00: 439269ccb6af62dd5be8c586243c6b706ba0fc6c46f323d3a0cf9321cc70de1f 0.600010000000 1411811 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": 952711, "vin": [ { "gen": { "height": 952701 } } ], "vout": [ { "amount": 600010000, "target": { "key": "439269ccb6af62dd5be8c586243c6b706ba0fc6c46f323d3a0cf9321cc70de1f" } } ], "extra": [ 1, 207, 210, 122, 99, 6, 98, 181, 223, 34, 65, 180, 165, 78, 181, 98, 78, 199, 101, 44, 136, 215, 217, 126, 232, 236, 182, 123, 178, 95, 233, 108, 27, 2, 17, 0, 0, 0, 5, 0, 17, 5, 91, 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