Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 65f31d73ae59768bb03aaebd57dff7193fb09e524a6b21c7cff1ea5152e6481d

Tx prefix hash: c55f72567735e4b28ee8198a6c446b863674d01f94837b3db6b59982b523087e
Tx public key: bd8b2241b75bf8108c382250174b8f756d65652cca1d2181d1ea9d1290fe03d6
Timestamp: 1729672044 Timestamp [UCT]: 2024-10-23 08:27:24 Age [y:d:h:m:s]: 00:187:14:42:38
Block: 1137711 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 133908 RingCT/type: yes/0
Extra: 01bd8b2241b75bf8108c382250174b8f756d65652cca1d2181d1ea9d1290fe03d6021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 192b99074a8c06d7413d857cf612df5bda989576fb0b0b4aa2e20fc2ce70d80d 0.600000000000 1621252 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": 1137721, "vin": [ { "gen": { "height": 1137711 } } ], "vout": [ { "amount": 600000000, "target": { "key": "192b99074a8c06d7413d857cf612df5bda989576fb0b0b4aa2e20fc2ce70d80d" } } ], "extra": [ 1, 189, 139, 34, 65, 183, 91, 248, 16, 140, 56, 34, 80, 23, 75, 143, 117, 109, 101, 101, 44, 202, 29, 33, 129, 209, 234, 157, 18, 144, 254, 3, 214, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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