Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b95e5e9fa6a183a615903f80608ffc8e64a3e90f71560cc1e97235542e2e5f0c

Tx prefix hash: 1de5b307966245a577b631c0aabf2431e7a7fd04343ace8d66a33fa3a1a91b13
Tx public key: 6b7e08dddbed03dcc2537ae7a7f60c15bca40dbc23d0dc5fd3836ee9b897523d
Timestamp: 1689516535 Timestamp [UCT]: 2023-07-16 14:08:55 Age [y:d:h:m:s]: 02:145:22:05:09
Block: 805098 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 624019 RingCT/type: yes/0
Extra: 016b7e08dddbed03dcc2537ae7a7f60c15bca40dbc23d0dc5fd3836ee9b897523d02110000000675e3f0e9000000000000000000

1 output(s) for total of 1.319399261000 dcy

stealth address amount amount idx
00: 47b15d35ab47315fdb9585cb9bd6bd8ed189cccc634d53219d671c57b37069d6 1.319399261000 1256317 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": 805108, "vin": [ { "gen": { "height": 805098 } } ], "vout": [ { "amount": 1319399261, "target": { "key": "47b15d35ab47315fdb9585cb9bd6bd8ed189cccc634d53219d671c57b37069d6" } } ], "extra": [ 1, 107, 126, 8, 221, 219, 237, 3, 220, 194, 83, 122, 231, 167, 246, 12, 21, 188, 164, 13, 188, 35, 208, 220, 95, 211, 131, 110, 233, 184, 151, 82, 61, 2, 17, 0, 0, 0, 6, 117, 227, 240, 233, 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