Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 73d3d8715a7b88422ab150a48d1ffc4b8fe3b7f3bf442036cafadd873106323e

Tx prefix hash: 235c3308841bad18e9cd8745dc9f43cd9891063a442d1dcc091f45d2e569e572
Tx public key: afc132b6981f4ff83c94c02248458d2f29f6d6c0c68d4a2463a58c2c2b50317f
Timestamp: 1700934088 Timestamp [UCT]: 2023-11-25 17:41:28 Age [y:d:h:m:s]: 01:089:22:50:56
Block: 899489 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 325409 RingCT/type: yes/0
Extra: 01afc132b6981f4ff83c94c02248458d2f29f6d6c0c68d4a2463a58c2c2b50317f0211000000014b8f5122000000000000000000

1 output(s) for total of 0.642124930000 dcy

stealth address amount amount idx
00: f13a7b4de7ad995e0aaae61b017f52e26320e3da12ee2d1d9f9c4441b904ee8c 0.642124930000 1355944 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": 899499, "vin": [ { "gen": { "height": 899489 } } ], "vout": [ { "amount": 642124930, "target": { "key": "f13a7b4de7ad995e0aaae61b017f52e26320e3da12ee2d1d9f9c4441b904ee8c" } } ], "extra": [ 1, 175, 193, 50, 182, 152, 31, 79, 248, 60, 148, 192, 34, 72, 69, 141, 47, 41, 246, 214, 192, 198, 141, 74, 36, 99, 165, 140, 44, 43, 80, 49, 127, 2, 17, 0, 0, 0, 1, 75, 143, 81, 34, 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