Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f99cb86e3b5411607dcaaa506cd5f3130466e995513608105d0ae30d0cc8c471

Tx prefix hash: c60e341d26b143ab230b12c7fc65f0034fc3ace701e3cdf096e12a3605fc43eb
Tx public key: 701c1d77ea2e0924033b67aa3e374bbd3a3de7d4324167ea77ef48e2f03126cb
Timestamp: 1721289196 Timestamp [UCT]: 2024-07-18 07:53:16 Age [y:d:h:m:s]: 00:262:20:46:49
Block: 1068256 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 187767 RingCT/type: yes/0
Extra: 01701c1d77ea2e0924033b67aa3e374bbd3a3de7d4324167ea77ef48e2f03126cb02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d93a0e1e121c65ce265e8ea976d03508d3418971f9a316b7949df81e0875ecec 0.600000000000 1539333 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": 1068266, "vin": [ { "gen": { "height": 1068256 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d93a0e1e121c65ce265e8ea976d03508d3418971f9a316b7949df81e0875ecec" } } ], "extra": [ 1, 112, 28, 29, 119, 234, 46, 9, 36, 3, 59, 103, 170, 62, 55, 75, 189, 58, 61, 231, 212, 50, 65, 103, 234, 119, 239, 72, 226, 240, 49, 38, 203, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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