Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0bc8165e00622d837e3e0735136eda1c8ea20f8c22cf2e1389939fb93afe5808

Tx prefix hash: 7792d6e525a4117de8c2b349b53e92c956940ff81e953c0a599188115eafd0de
Tx public key: 6f5ebcda4e7f31c5bc97a295743d2c14d2f24f2aebfc04a90d629a66d372a178
Timestamp: 1717173639 Timestamp [UCT]: 2024-05-31 16:40:39 Age [y:d:h:m:s]: 00:225:22:46:40
Block: 1034125 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 161702 RingCT/type: yes/0
Extra: 016f5ebcda4e7f31c5bc97a295743d2c14d2f24f2aebfc04a90d629a66d372a178021100000002679a8a81000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1e1abbfd72902ef560820247bf75d4481115509957da29fb7314b78dd3fe79f2 0.600000000000 1502604 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": 1034135, "vin": [ { "gen": { "height": 1034125 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1e1abbfd72902ef560820247bf75d4481115509957da29fb7314b78dd3fe79f2" } } ], "extra": [ 1, 111, 94, 188, 218, 78, 127, 49, 197, 188, 151, 162, 149, 116, 61, 44, 20, 210, 242, 79, 42, 235, 252, 4, 169, 13, 98, 154, 102, 211, 114, 161, 120, 2, 17, 0, 0, 0, 2, 103, 154, 138, 129, 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